Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | GitHubAuditBlobConnector |
| Publisher | Microsoft |
| Used in Solutions | GitHub |
| Collection Method | CCF |
| Connector Definition Files | ConnectorDefinition.json |
| DCR Definition Files | DCR.json |
| CCF Configuration | PollingConfig.json |
| CCF Capabilities | StorageAccountBlobContainer, ServicePrincipal |
| Microsoft Learn | View on Learn |
The GitHub audit log connector ingests GitHub Enterprise audit logs into Microsoft Sentinel from Azure Blob Storage with near real-time latency. GitHub streams audit logs to Blob Storage in near real time, and the connector polls the Azure Storage Queue for new blob-created notifications every 5 minutes (default polling interval). By connecting GitHub audit logs to Microsoft Sentinel, you can view this data in workbooks, create custom alerts, and improve your investigation process.
Azure Government Cloud: This connector is not supported in Azure Government Cloud. GitHub documentation states: "Audit log streaming to blob storage in Azure Government is not supported".
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
GitHubAuditLogsV3_CL |
✓ | ✓ | ✓ |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Resource Provider Permissions:
Custom Permissions:
Note: The
Microsoft.EventGridresource provider must be registered in the subscription containing the storage account.
Note: This is a one-time action per tenant. If the service principal already exists (i.e., another connector using ScubaSentinelToStorageProd was previously configured in this tenant), the service principal ID will be auto-populated and no action is needed.
If using NSP: Only Transition access mode is supported. In the NSP's Associated resources, set the storage account's access mode to Transition, and keep Enabled from all networks on the storage account. Transition mode falls back to the storage account's network rules.
For general guidance, see Enable Network Security for Azure Storage Blob Connectors.
Choose Create to grant that identity Storage Queue Data Message Sender on the destination storage account, or Use existing to skip creating the sender grant when the identity already has that permission, as required by Event Grid Storage Queue delivery. Use Create for a new topic or a newly enabled system-assigned identity. Account-scoped sender access allows adding messages to queues in that account, not reading or deleting messages or accessing blobs. This identity is separate from the existing ScubaSentinelToStorageProd collector application, which remains unchanged and continues to read blobs and consume queue messages.
To assign these roles: navigate to the Storage Account -> Access Control (IAM) -> Add role assignment, search for the service principal ID shown below, and assign both roles.
Collecting GitHub audit logs to your blob container: Follow the steps in the GitHub documentation to configure audit log streaming to your Azure Blob Storage container.
When following the guidance to generate a SAS token, two signing methods are supported: Account key and User delegation key.
For the Account key method, we recommend first creating a Stored Access Policy and then generating the SAS tied to that policy.
Binding the SAS to a policy lets you change its expiry and permissions, or revoke it, on the server side. This enables seamless rotation by updating the policy rather than reissuing the token.
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
1. Connect GitHub Audit Logs to Microsoft Sentinel
Use the connection grid to add and manage GitHub Audit Log blob connections. Connector Management Interface
This section is an interactive interface in the Microsoft Sentinel portal that allows you to manage your data collectors.
📊 View Existing Collectors: A management table displays all currently configured data collectors with the following information:
➕ Add New Collector: Click the "Add new collector" button to configure a new data collector (see configuration form below).
🔧 Manage Collectors: Use the actions menu to delete or modify existing collectors.
💡 Portal-Only Feature: This configuration interface is only available when viewing the connector in the Microsoft Sentinel portal. You cannot configure data collectors through this static documentation.
Connect GitHub Audit Logs to Microsoft Sentinel
Provide the required storage information for a new connection.
When you click the "Add Connection" button in the portal, a configuration form will open. You'll need to provide:
Connection configuration
RBAC propagation: If Connect fails with Managed Identity Authorization Error, wait about five minutes and retry with the same values. Propagation can take up to ten minutes.
💡 Portal-Only Feature: This configuration form is only available in the Microsoft Sentinel portal.
2. Blob Lifecycle Policy (Recommended)
To prevent unbounded storage growth, configure a lifecycle management policy on your storage account to automatically delete blobs after a retention period (for example, 7 days). Once the connector ingests the audit logs into Microsoft Sentinel, the source blobs are no longer needed.
To create a lifecycle rule scoped to your container:
github-audit-cleanupmy-container/). This ensures the rule applies only to blobs in that container.Note: Each storage account has a single management policy that can contain multiple rules. Each rule can target a specific container via prefix filters. If you already have a lifecycle policy, add a new rule to the existing policy rather than creating a new one.
3. Reference
For detailed instructions on setting up the Azure Storage connector to stream logs to Microsoft Sentinel, see Set up Azure Storage connector.
4. Troubleshooting
If you encounter issues with data ingestion:
RBAC propagation: If Connect fails with Managed Identity Authorization Error, wait about five minutes and retry with the same values. Propagation can take up to ten minutes.
5. Limitations
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊